Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ISPN-13181 JDK 17 changes (Nashorn) #9450

Merged
merged 2 commits into from
Sep 15, 2021

Conversation

tristantarrant
Copy link
Member

@tristantarrant tristantarrant commented Jul 19, 2021

@tristantarrant
Copy link
Member Author

I'll add JDK 17 to the CI slaves as soon as PSI comes back from the dead...

@tristantarrant
Copy link
Member Author

Copy link
Member

@wburns wburns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tristantarrant
Copy link
Member Author

Because that CI job is running against main. Let me redirect it

@tristantarrant tristantarrant force-pushed the ISPN-13181/jdk17_nashorn branch 2 times, most recently from 224a7b9 to 6703923 Compare July 29, 2021 09:13
@ryanemerson
Copy link
Contributor

It looks like Nashorn needs to be added to the client classpath for tests. There are also various IT failures.

@tristantarrant tristantarrant changed the title ISPN-13181 + ISPN-13182 JDK 17 changes (Nashorn + BlockHound) ISPN-13182 JDK 17 changes (Nashorn) Sep 8, 2021
@ryanemerson
Copy link
Contributor

Further changes required. 74 failures atm.

@tristantarrant
Copy link
Member Author

Please ignore the thirdparty failures as they will be fixed when WF 25 is out (https://issues.redhat.com/browse/WFCORE-5406)

@tristantarrant
Copy link
Member Author

tristantarrant commented Sep 13, 2021

This is good to go. Before merging I need to remove the commit that modifies Jenkinsfile

Copy link
Contributor

@ryanemerson ryanemerson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of minor things, but it should be ok to remove the Jenkins commit and merge if the normal CI run is fine.

@@ -191,6 +193,7 @@ public void testScriptUpload() {

@Test
public void testExecScripts() {
SkipJunit.skipSinceJDK(16);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't we still need to test this functionality with 17?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding the nashorn dependencies will force us to run all these tests in Container mode, but we don't have a JDK 17 container yet.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok. I've created ISPN-13269 so this isn't missed.

@ryanemerson
Copy link
Contributor

Also, I think ISPN-13182 is the wrong Jira ID as that has already been resolved and relates to blockhound.

@tristantarrant tristantarrant changed the title ISPN-13182 JDK 17 changes (Nashorn) ISPN-13181 JDK 17 changes (Nashorn) Sep 13, 2021
@ryanemerson
Copy link
Contributor

org.infinispan.server.configuration.ServerOverlayConfigurationTest.testOverlay Is failing.

Also, shouldn't the *.thirdparty.* tests only fail with JDK 17?

@tristantarrant
Copy link
Member Author

I did not modify the Jenkinsfile yet

@ryanemerson
Copy link
Contributor

I did not modify the Jenkinsfile yet

Argh sorry, I should have explicitly checked that! I just saw that the number of commits had reduced and assumed.

@tristantarrant
Copy link
Member Author

I have added a commit which fixes the NPE in org.infinispan.server.configuration.ServerOverlayConfigurationTest.testOverlay

@tristantarrant
Copy link
Member Author

Once CI is done I'll remove the Jenkinsfile commit

@tristantarrant
Copy link
Member Author

@ryanemerson I've repushed it without the Jenkinsfile change

@ryanemerson
Copy link
Contributor

There's a ClassNotFoundException with org.infinispan.commons.test.skip.SkipJunit that needs to be resolved.

@tristantarrant
Copy link
Member Author

There's a ClassNotFoundException with org.infinispan.commons.test.skip.SkipJunit that needs to be resolved.

Fixed

@tristantarrant
Copy link
Member Author

@ryanemerson lgtm

@ryanemerson
Copy link
Contributor

RemoteCacheMetricBinderTest is consistently failing on the last few runs and does not appear to be an issue on main.

Could you squash the NPE commits into ISPN-13181.

Also, I think ISPN-13182 is the wrong Jira ID as that has already been resolved and relates to blockhound.

This also needs addressing.

@tristantarrant
Copy link
Member Author

Silly me: I had made a change to the default infinispan.xml file

@tristantarrant
Copy link
Member Author

I created an extra Jira and squashed the NPE commits

@ryanemerson
Copy link
Contributor

The four UNKNOWN.ThreadLeakChecker failures are also consistently failing on this PR and aren't present on main.

* Use the standalone Nashorn dependency
* Run relevant server tests in container
* Upgrade XOM as a Workaround for Galleon plugin
* Use WildFly 24.0.1
@tristantarrant
Copy link
Member Author

The arquillian upgrade has changed the class of the ConsoleConsumer thread. I've fixed it

@ryanemerson ryanemerson merged commit b075d48 into infinispan:main Sep 15, 2021
@ryanemerson
Copy link
Contributor

Thanks @tristantarrant

@gustavocoding
Copy link

There was a possible related failure in org.infinispan.server.functional.RollingUpgradeDynamicStoreCliIT.testRollingUpgrade

@tristantarrant tristantarrant deleted the ISPN-13181/jdk17_nashorn branch July 5, 2022 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants